Skip to content

backlog: P3 — is UML modelling useful for the factory + what tools to map?#173

Merged
AceHack merged 1 commit intomainfrom
backlog/uml-modeling-utility-research
Apr 23, 2026
Merged

backlog: P3 — is UML modelling useful for the factory + what tools to map?#173
AceHack merged 1 commit intomainfrom
backlog/uml-modeling-utility-research

Conversation

@AceHack
Copy link
Copy Markdown
Member

@AceHack AceHack commented Apr 23, 2026

Summary

Adds a P3 BACKLOG row capturing the human maintainer's 2026-04-23 question:

"backlog is uml modeling useful for the factory and what tools would it require us map?"

Two-question research pointer:

  1. Utility — does UML add value on top of OpenSpec (behavioural specs) + formal-spec stack (TLA+, Lean, Z3, FsCheck, Alloy) the factory already has?
  2. Tooling-map — if we adopt, what tools enter docs/FACTORY-TECHNOLOGY-INVENTORY.md (PlantUML / Mermaid / draw.io / Structurizr / Rational Rose lineage)?

First-pass recommendation (to validate)

  • Mermaid — factory-aligned default: git-native, renders in GitHub, zero toolchain, no new language
  • PlantUML — richer expressiveness but needs Java (new language)
  • Structurizr — architecture-as-code framing
  • Heavy UML tools (Rational Rose / Enterprise Architect / MagicDraw) — likely over-scoped for a factory already fluent in formal specs

Composes with

Research note under docs/research/uml-modelling-for-the-factory-YYYY-MM-DD.md when prioritised. No adopt commitment. Effort S for first-pass; M if adopting.

🤖 Generated with Claude Code

Copilot AI review requested due to automatic review settings April 23, 2026 17:31
@AceHack AceHack enabled auto-merge (squash) April 23, 2026 17:31
AceHack added a commit that referenced this pull request Apr 23, 2026
Aaron: "backlog is uml modeling useful for the factory and
what tools would it require us map?"

Filed as P3 row with two-question research pointer (utility
vs existing OpenSpec + formal-spec discipline; tooling-map
for factory-technology-inventory). First-pass recommendation:
Mermaid as factory-aligned default (git-native, zero
toolchain). Auto-merge armed.

Adjacent to Rational Rose P3 row (PR #163) — both will sit
together on merge; row #54 first firing likely flags for
consolidation consideration.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new P3 BACKLOG entry to capture a research question about whether UML modelling is useful for the factory and, if so, which tooling would need to be inventoried alongside the existing spec/formal-verification stack.

Changes:

  • Add a new P3 backlog bullet describing the UML utility question and a tooling-map question.
  • Include an initial (non-binding) recommendation comparing Mermaid, PlantUML, Structurizr, and heavier UML tools.
  • Add cross-references to related planned inventory/docs work and adjacent backlog items.

Comment thread docs/BACKLOG.md
Comment thread docs/BACKLOG.md Outdated
Comment thread docs/BACKLOG.md
Comment thread docs/BACKLOG.md
Aaron 2026-04-23: "backlog is uml modeling useful for the
factory and what tools would it require us map?"

Two-question research pointer:
1. Utility — does UML add value on top of OpenSpec + formal
   specs (TLA+ / Lean / Z3 / FsCheck / Alloy)?
2. Tooling-map — if we adopt, what tools would the factory
   inventory (PlantUML / Mermaid / draw.io / Structurizr /
   Rational Rose lineage)?

Composes with:
- Rational Rose P3 row (adjacent when PR #163 merges)
- docs/FACTORY-TECHNOLOGY-INVENTORY.md (PR #170 target)
- OpenSpec workflow (spec-as-source-of-truth already in
  place)
- Formal-spec stack

First-pass recommendation (to validate): Mermaid is the
factory-aligned default (git-native, zero toolchain, GitHub
renders natively); heavy UML tools likely over-scoped.

Research note under docs/research/uml-modelling-for-the-
factory-YYYY-MM-DD.md when prioritised. No adopt commitment.
No deadline. Effort S first-pass; M if adopting.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@AceHack AceHack force-pushed the backlog/uml-modeling-utility-research branch from 342be44 to e63efc8 Compare April 23, 2026 18:07
@AceHack AceHack merged commit 78b28b9 into main Apr 23, 2026
10 checks passed
@AceHack AceHack deleted the backlog/uml-modeling-utility-research branch April 23, 2026 18:09
AceHack added a commit that referenced this pull request Apr 23, 2026
…lassification BACKLOG

13 session PRs merged. Three landed in ~4 minutes: #159
(Overlay A #3), #172 (Pages-UI BACKLOG), #173 (UML BACKLOG).

PR #173 unblock: 4 findings — Rational Rose cross-ref
stale after rebase (row now adjacent on main); grammar nit
fixed; row-number accepted as current; hard-coded row #49
kept. 4 threads resolved.

Aaron directive (two-message): age-classification skill
covering language + concepts. Filed PR #176 as P3 row,
captures both axes + bi-audience (AI + humans) + human-
standards-mapping + new physiology-based factory standard.
Auto-merge armed.

Rational Rose + UML rows now adjacent on main — prime
target for row #54 first-fire overlap sweep.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants